.dtx files which need
to be unpacked using docstrip to create user files. The
resulting .sty files change the font defaults to use some new
group of fonts (sometimes just one default is changed).
Scripts are provided for docstrip in the form of .ins files, which simply need to be run through TEX; when that has been done, install all the .sty files that result in a directory where LATEX will find them.
You have an important decision to make at some point — are you going to use fonts encoded in the `Cork' layout, or the old ones which look like the CM fonts described in the TEX book? This manual will not attempt to explain why you should or should not use Cork fonts... Font description (.fd) files are available for both T1 and OT1 encoding in the CTAN fonts/psfonts directories.
If you follow the Cork-encoding route, you need different TEX font metric files and virtual font files. To activate this, use the package t1enc.
Important. If you use the Cork (T1 in LATEX2e scheme) encoding, you will probably also need the EC fonts to go with them, for maths and so on.
The standard `35' POSTSCRIPT fonts built into most POSTSCRIPT printers are known by their `Berry' names:
Family name Full name pag Adobe AvantGarde pbk Adobe Bookman pcr Adobe Courier phv Adobe Helvetica pnc Adobe NewCenturySchoolbook ppl Adobe Palatino ptm Adobe TimesRoman pzc Adobe ZapfChancery psy Adobe Symbol font pzd Adobe ZapfDingbats
To create font and package files for Lucida and Lucida Bright (including Lucida Bright maths), run TEX on lucida.ins.